Skip to content

fix: unable to match assets when filename contains special characters#385

Merged
icelam merged 1 commit intodevelopfrom
issue-353-special-characters
Jul 24, 2022
Merged

fix: unable to match assets when filename contains special characters#385
icelam merged 1 commit intodevelopfrom
issue-353-special-characters

Conversation

@icelam
Copy link
Copy Markdown
Owner

@icelam icelam commented Jul 24, 2022

Description

Attempt to fix issue #353 where the plugin fails to handle file name with special characters like @.

The root cause of the issue is that filename extracted from tag src attribute is a URI encoded string (e.g. 'index%40production.js'), so this PR aims to solve it by adding a decoding step when accessing the assets object from webpack.

How has this been tested?

  1. A new test case where it's configuration has all JavaScript assets output with @ in the filename is added. This is check and run to make sure the output files are properly inlined.

Types of changes

  • New feature - feat
  • Bug fix - fix
  • Refactor - refactor
  • Test cases - test
  • Other(s):

Remarks

N/A

@icelam icelam force-pushed the issue-353-special-characters branch from a773315 to ab830c1 Compare July 24, 2022 08:24
@icelam icelam force-pushed the issue-353-special-characters branch from ab830c1 to ce6be9c Compare July 24, 2022 08:31
@icelam icelam merged commit d7c4d79 into develop Jul 24, 2022
@icelam icelam deleted the issue-353-special-characters branch July 24, 2022 09:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant